Skip to content

chore: exclude internal/development files from crate package#15

Merged
mikkihugo merged 2 commits into
mainfrom
chore/exclude-dev-files-from-crate
Nov 11, 2025
Merged

chore: exclude internal/development files from crate package#15
mikkihugo merged 2 commits into
mainfrom
chore/exclude-dev-files-from-crate

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Nov 11, 2025

Analyzing changes...

Commits:

  • chore: exclude internal/development files from crate package

Changed Files:

Cargo.toml | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)

Detailed Changes:

@mikkihugo
chore: exclude internal/development files from crate package
1389503 
Exclude from crate releases:
- Git hooks and config (.githooks/, .gitignore, .gitmessage)
- Development tools (renovate.json5, clippy.toml, deny.toml, build.rs)
- Organization template directory (org-repos-setup/)
- Internal documentation (Claude setup, CI optimization, workflow guides, etc.)
- CHANGELOG.md (included separately in GitHub releases)

This ensures only essential library files are distributed in the crate package.
@mikkihugo
chore: remove redundant org-repos-setup directory
dc1c339 
The org-level .github repository (Singularity-ng/.github) is already set up with the same workflow templates and organization files. This directory was just a duplicate/template that's no longer needed.
@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Nov 11, 2025

🔍 Automated Checks

🔍 Checking for stale files and out-of-scope changes...

Stale File Check

✅ No stale files detected

Scope Check

Checking file relevance (blocks binaries, temp files, etc.)...

✅ All changes appear relevant (includes .github/ workflows, src/, docs, config)

Claude is reviewing the code... Check the "Claude Code Review" step for detailed feedback.

mikkihugo
mikkihugo approved these changes Nov 11, 2025
View reviewed changes
Copy link
Copy Markdown
Contributor

@mikkihugo mikkihugo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Claude AI approved this PR! All checks passed. Will auto-merge when CI is green.

@mikkihugo mikkihugo enabled auto-merge (squash) November 11, 2025 08:22
@mikkihugo mikkihugo merged commit 2cc82fd into main Nov 11, 2025
9 checks passed
@mikkihugo mikkihugo deleted the chore/exclude-dev-files-from-crate branch November 11, 2025 08:27
@qodo-code-review
Copy link
Copy Markdown

qodo-code-review Bot commented Nov 11, 2025

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢
No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪
🎫 No ticket provided
  • Create ticket/issue
Codebase Duplication Compliance
⚪
Codebase context is not defined

Follow the guide to enable codebase context checks.

Custom Compliance
⚪
Generic: Comprehensive Audit Trails

Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.

Status:
Non-runtime change: The new additions only modify the crate packaging exclude list and do not introduce or
modify runtime behavior or logging, so audit trail compliance cannot be evaluated from
this diff alone.

Referred Code 
".githooks/",
".gitignore",
".gitmessage",
"renovate.json5",
"clippy.toml",
"deny.toml",
"build.rs",

# Build artifacts
"release-reports/",
"target/",
"*.profraw",
"*.profdata",

# Organization/template setup files
"org-repos-setup/",

# Documentation (internal/setup guides - not for end users)
"DOCS_SETUP.md",
"WORKFLOWS_SETUP.md",
"AUTO_MERGE_FLOW.md",


 ... (clipped 20 lines)

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Meaningful Naming and Self-Documenting Code

Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting

Status:
No identifiers added: The diff only adds entries to the Cargo package exclude list and does not introduce code
identifiers, so naming conventions cannot be assessed from this change.

Referred Code 
".githooks/",
".gitignore",
".gitmessage",
"renovate.json5",
"clippy.toml",
"deny.toml",
"build.rs",

# Build artifacts
"release-reports/",
"target/",
"*.profraw",
"*.profdata",

# Organization/template setup files
"org-repos-setup/",

# Documentation (internal/setup guides - not for end users)
"DOCS_SETUP.md",
"WORKFLOWS_SETUP.md",
"AUTO_MERGE_FLOW.md",


 ... (clipped 20 lines)

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Robust Error Handling and Edge Case Management

Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation

Status:
No error paths: The changes are configuration for packaging excludes and do not add executable logic or
error handling paths, so robustness cannot be evaluated from this diff.

Referred Code 
".githooks/",
".gitignore",
".gitmessage",
"renovate.json5",
"clippy.toml",
"deny.toml",
"build.rs",

# Build artifacts
"release-reports/",
"target/",
"*.profraw",
"*.profdata",

# Organization/template setup files
"org-repos-setup/",

# Documentation (internal/setup guides - not for end users)
"DOCS_SETUP.md",
"WORKFLOWS_SETUP.md",
"AUTO_MERGE_FLOW.md",


 ... (clipped 20 lines)

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Error Handling

Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.

Status:
No user errors: No user-facing error messages were added or modified; only packaging excludes were
updated, so secure error handling cannot be assessed from this change.

Referred Code 
".githooks/",
".gitignore",
".gitmessage",
"renovate.json5",
"clippy.toml",
"deny.toml",
"build.rs",

# Build artifacts
"release-reports/",
"target/",
"*.profraw",
"*.profdata",

# Organization/template setup files
"org-repos-setup/",

# Documentation (internal/setup guides - not for end users)
"DOCS_SETUP.md",
"WORKFLOWS_SETUP.md",
"AUTO_MERGE_FLOW.md",


 ... (clipped 20 lines)

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Logging Practices

Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.

Status:
No logging added: The diff does not introduce or modify logging; it only excludes files from the crate
package, so logging practices cannot be evaluated here.

Referred Code 
".githooks/",
".gitignore",
".gitmessage",
"renovate.json5",
"clippy.toml",
"deny.toml",
"build.rs",

# Build artifacts
"release-reports/",
"target/",
"*.profraw",
"*.profdata",

# Organization/template setup files
"org-repos-setup/",

# Documentation (internal/setup guides - not for end users)
"DOCS_SETUP.md",
"WORKFLOWS_SETUP.md",
"AUTO_MERGE_FLOW.md",


 ... (clipped 20 lines)

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Security-First Input Validation and Data Handling

Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities

Status:
No input handling: No input processing or data handling code was added; only Cargo package exclude patterns
changed, so security validation cannot be assessed from this diff.

Referred Code 
".githooks/",
".gitignore",
".gitmessage",
"renovate.json5",
"clippy.toml",
"deny.toml",
"build.rs",

# Build artifacts
"release-reports/",
"target/",
"*.profraw",
"*.profdata",

# Organization/template setup files
"org-repos-setup/",

# Documentation (internal/setup guides - not for end users)
"DOCS_SETUP.md",
"WORKFLOWS_SETUP.md",
"AUTO_MERGE_FLOW.md",


 ... (clipped 20 lines)

Learn more about managing compliance generic rules or creating your own custom rules
Compliance status legend 🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mikkihugo mikkihugo mikkihugo approved these changes

Assignees

No one assigned

Labels

Review effort 2/5

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@mikkihugo